Skip to content

OCPBUGS-43686: UPSTREAM: <carry>: Fix go-retryablehttp CVE - 4.16 #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

Karthik-K-N
Copy link
Member

No description provided.

@openshift-ci openshift-ci bot requested review from JoelSpeed and nrb October 18, 2024 07:33
Copy link
Contributor

openshift-ci bot commented Oct 18, 2024

@Karthik-K-N: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@Karthik-K-N Karthik-K-N changed the title UPSTREAM: <carry>: Fix go-retryablehttp CVE OCPBUGS-43686: UPSTREAM: <carry>: Fix go-retryablehttp CVE - 4.16 Oct 22, 2024
@openshift-ci-robot
Copy link

@Karthik-K-N: An error was encountered searching for bug OCPBUGS-43686 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@prb112
Copy link
Contributor

prb112 commented Oct 24, 2024

/jira refresh

@openshift-ci-robot
Copy link

@prb112: An error was encountered searching for bug OCPBUGS-43686 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@Karthik-K-N
Copy link
Member Author

4.17 PR has been merged and included in the build, so any help here
@sunzhaohua2

@JoelSpeed
Copy link
Contributor

/lgtm
/approve
/label backport-risk-assessed

Waiting on 4.17 patch to go through QE before adding Jira labels

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 28, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 28, 2024
Copy link
Contributor

openshift-ci bot commented Oct 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2024
@Karthik-K-N
Copy link
Member Author

/lgtm /approve /label backport-risk-assessed

Waiting on 4.17 patch to go through QE before adding Jira labels

4.17 bug moved into verfied state https://issues.redhat.com/browse/OCPBUGS-37369

@JoelSpeed JoelSpeed added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Nov 1, 2024
@JoelSpeed
Copy link
Contributor

Ready fro QE to take a look now then

@sunzhaohua2
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 4, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 7d4f93e into openshift:release-4.16 Nov 4, 2024
5 checks passed
@openshift-ci-robot
Copy link

@Karthik-K-N: An error was encountered searching for bug OCPBUGS-43686 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. You do not have the permission to see the specified issue.: request failed. Please analyze the request body for more details. Status code: 403:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-ibmcloud-cluster-api-controllers
This PR has been included in build ose-ibmcloud-cluster-api-controllers-container-v4.16.0-202411040206.p0.g7d4f93e.assembly.stream.el9.
All builds following this will include this PR.

@Karthik-K-N
Copy link
Member Author

PR changes has been included in build , Looking forward for help in subsequent PRs to other branches #87

@sunzhaohua2
Copy link

Sorry, not sure why pr merged but bug is still in Post status, I will verify this 4.16 bug.

@Karthik-K-N
Copy link
Member Author

Sorry, not sure why pr merged but bug is still in Post status, I will verify this 4.16 bug.

No Problem, Thank you. We wanted to close all the CVE PRs so seeking help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants